System and method for registering entities for code signing services

ABSTRACT

A system and method for registering entities for code signing services. The entities may be software application developers or other individuals or entities that wish to have applications digitally signed. Signing of the applications may be required in order to enable the applications to access sensitive APIs and associated resources of a computing device when the applications are executed on the computing device. In one embodiment, a method of registering entities for code signing services will comprise the step of transmitting at least some account data to the registering individual or entity using an out-of-band communication system. This provides added security that the individual or entity registering for a code signing service is who that individual or entity purports to be.

A portion of the disclosure of this patent document contains materialwhich is subject to copyright protection. The copyright owner has noobjection to the facsimile reproduction by anyone of the patent documentor the patent disclosure, as it appears in the Patent and TrademarkOffice patent file or records, but otherwise reserves all copyrightrights whatsoever.

FIELD OF THE INVENTION

Embodiments of the systems and methods described herein relate generallyto the field of security protocols for software applications, and morespecifically to a system and method for providing code signing servicesto individuals or entities that wish to have software applicationsdigitally signed in order that the applications may be executed on acomputing device (e.g. a mobile device).

BACKGROUND OF THE INVENTION

Security protocols involving software code signing schemes are typicallyused to ensure the reliability of software applications that aredownloaded from the Internet or other sources for execution on acomputing device. The computing device may be, for example, a mobiledevice.

A code signing system may be implemented on a computing device tocontrol access to certain resources on the computing device by asoftware application. In one example system, there is provided on thecomputing device an application platform, one or more applicationprogramming interfaces (APIs), and a virtual machine. The APIs areconfigured to link software applications with the application platform,and more specifically, to allow software applications to make functioncalls to or otherwise interact with resources made generally accessibleto software applications on the computing device.

However, some of the APIs may be classified as “sensitive” by entitiesthat wish to restrict access to those APIs or to the particularresources associated with those APIs. In the example system, the virtualmachine is adapted to verify the authenticity of a digital signatureappended to an application requiring access to a sensitive API beforeaccess to the sensitive API is granted. Accordingly, in order for anapplication to be granted access to the sensitive API, an appropriatesigning authority must first digitally sign the application.

BRIEF DESCRIPTION OF THE DRAWINGS

For a better understanding of the embodiments of the systems and methodsdescribed herein, and to show more clearly how they may be carried intoeffect, reference will now be made, by way of example, to theaccompanying drawings in which:

FIG. 1 is a block diagram of a mobile device in one exampleimplementation;

FIG. 2 is a block diagram of a communication subsystem component of themobile device of FIG. 1;

FIG. 3 is a block diagram of a node of a wireless network;

FIG. 4 is a diagram illustrating an example code signing protocol inwhich a code signing authority provides code signing services to asoftware application developer;

FIG. 5 is a diagram illustrating components of an example code signingsystem on a mobile device;

FIG. 6 is a flowchart illustrating steps in an example method ofprocessing signed software applications performed on the mobile devicedepicted in FIG. 5;

FIG. 7A is a flowchart illustrating steps in a method of providing codesigning services in one embodiment;

FIG. 7B is a schematic diagram illustrating a system for providing codesigning services in an example network configuration;

FIG. 8A is a flowchart illustrating steps in a method of creating a keypair for code signing in one embodiment;

FIGS. 8B and 8C are example dialog boxes in a user interface provided bya code signing authority application;

FIG. 9 is a flowchart illustrating steps in a method of registering anentity for code signing services in one embodiment; and

FIG. 10 is an example form illustrating details of an account record.

DETAILED DESCRIPTION

Software application developers who create applications that wouldrequire access to sensitive APIs on a computing device may need to havetheir applications digitally signed by an appropriate signing authority,so that the applications will properly execute on the computing device.An entity that wishes to restrict access to certain sensitive APIs (andassociated resources), such as proprietary APIs that the entity itselfmay have authored for example, may wish to act as a signing authority inrespect of those APIs and provide code signing services to the softwareapplication developers requiring access to those APIs. Through theprovision of code signing services, an entity can control who should andshould not be granted access to specific APIs that it has authoredand/or classified as sensitive, track who has requested such access, andcharge for providing such access if desired, for example.

Embodiments described herein relate generally to a system and method forproviding code signing services to software application developers or toother individuals or entities that wish to have applications digitallysigned. Signing of the applications may be required in order to enablethe applications to access sensitive APIs and associated resources of acomputing device when the applications are executed on the computingdevice.

Code signing authorities that provide code signing services to softwareapplication developers or to other individuals or entities may requirethat these parties register for code signing services. These individualsor entities, at the time of registration, may provide a public key foruse in communicating securely with the code signing authority. Acost-effective and timely technique that may be employed to verify thatthe public key being provided belongs to the associated registrant isdesirable.

In one aspect, there is provided a method of registering entities forcode signing services, the method comprising the steps of: receiving aregistration request from an entity requesting registration for codesigning services, wherein the registration request includes dataassociated with the identity of the entity; authenticating the identityof the entity by validating at least a subset of the data in theregistration request; generating an account record for the entity,wherein the account record comprises at least a first and a secondidentifier associated with the entity; transmitting one of the first andsecond identifiers to the entity via a first communication channel andthe other of the first and second identifiers via a different, secondcommunication channel; receiving a registration file from the entity;and confirming that the registration file includes at least both of thefirst and second identifiers prior to accepting the registrationrequest.

The computing device upon which signed applications are executed may bea mobile station, for example. However, it will be understood by personsskilled in the art that at least some of the embodiments describedherein may be implemented in respect of applications that are to beexecuted on computing devices other than mobile stations.

A mobile station is a two-way communication device with advanced datacommunication capabilities having the capability to communicate withother computer systems, and is also referred to herein generally as amobile device. A mobile device may also include the capability for voicecommunications. Depending on the functionality provided by a mobiledevice, it may be referred to as a data messaging device, a two-waypager, a cellular telephone with data messaging capabilities, a wirelessInternet appliance, or a data communication device (with or withouttelephony capabilities). A mobile device communicates with other devicesthrough a network of transceiver stations. To aid the reader inunderstanding the structure of a mobile device and how it communicateswith other devices, reference is made first to FIGS. 1 through 3.

Referring to FIG. 1, a block diagram of a mobile device in one exampleimplementation is shown generally as 100. Mobile device 100 comprises anumber of components, the controlling component being microprocessor102. Microprocessor 102 controls the overall operation of mobile device100. Communication functions, including data and voice communications,are performed through communication subsystem 104. Communicationsubsystem 104 receives messages from and sends messages to a wirelessnetwork 200. In this example implementation of mobile device 100,communication subsystem 104 is configured in accordance with the GlobalSystem for Mobile Communication (GSM) and General Packet Radio Services(GPRS) standards. The GSM/GPRS wireless network is used worldwide and itis expected that these standards will be superseded eventually byEnhanced Data GSM Environment (EDGE) and Universal MobileTelecommunications Service (UMTS). New standards are still beingdefined, but it is believed that they will have similarities to thenetwork behavior described herein, and it will also be understood bypersons skilled in the art that other suitable standards that aredeveloped in the future may be used. The wireless link connectingcommunication subsystem 104 with network 200 represents one or moredifferent Radio Frequency (RF) channels, operating according to definedprotocols specified for GSM/GPRS communications. With newer networkprotocols, these channels are capable of supporting both circuitswitched voice communications and packet switched data communications.

Although the wireless network associated with mobile device 100 is aGSM/GPRS wireless network in one example implementation of mobile device100, other wireless networks may also be associated with mobile device100 in variant implementations. Different types of wireless networksthat may be employed include, for example, data-centric wirelessnetworks, voice-centric wireless networks, and dual-mode networks thatcan support both voice and data communications over the same physicalbase stations. Combined dual-mode networks include, but are not limitedto, Code Division Multiple Access (CDMA) or CDMA2000 networks, GSM/GPRSnetworks (as mentioned above), and future third-generation (3G) networkslike EDGE and UMTS. Some older examples of data-centric networks includethe Mobitex™ Radio Network and the DataTAC™ Radio Network. Examples ofolder voice-centric data networks include Personal Communication Systems(PCS) networks like GSM and Time Division Multiple Access (TDMA)systems.

Microprocessor 102 also interacts with additional subsystems such as aRandom Access Memory (RAM) 106, flash memory 108, display 110, auxiliaryinput/output (I/O) subsystem 112, serial port 114, keyboard 116, speaker118, microphone 120, short-range communications subsystem 122 and otherdevices 124.

Some of the subsystems of mobile device 100 performcommunication-related functions, whereas other subsystems may provide“resident” or on-device functions. By way of example, display 110 andkeyboard 116 may be used for both communication-related functions, suchas entering a text message for transmission over network 200, anddevice-resident functions such as a calculator or task list. Operatingsystem software used by microprocessor 102 is typically stored in apersistent store such as flash memory 108, which may alternatively be aread-only memory (ROM) or similar storage element (not shown). Thoseskilled in the art will appreciate that the operating system, specificdevice applications, or parts thereof, may be temporarily loaded into avolatile store such as RAM 106.

Mobile device 100 may send and receive communication signals overnetwork 200 after required network registration or activation procedureshave been completed. Network access is associated with a subscriber oroperator of a mobile device 100. To identify a subscriber, mobile device100 requires a Subscriber Identity Module or “SIM” card 126 to beinserted in a SIM interface 128 in order to communicate with a network.SIM 126 is one type of a conventional “smart card” used to identify asubscriber of mobile device 100 and to personalize the mobile device100, among other things. Without SIM 126, mobile device 100 is not fullyoperational for communication with network 200. By inserting SIM 126into SIM interface 128, a subscriber can access all subscribed services.Services could include: web browsing and messaging such as e-mail, voicemail, Short Message Service (SMS), and Multimedia Messaging Services(MMS). More advanced services may include: point of sale, field serviceand sales force automation. SIM 126 includes a processor and memory forstoring information. Once SIM 126 is inserted in SIM interface 128, itis coupled to microprocessor 102. In order to identify the subscriber,SIM 126 contains some parameters such as an International MobileSubscriber Identity (IMSI). An advantage of using SIM 126 is that asubscriber is not necessarily bound by any single physical mobiledevice. SIM 126 may store additional subscriber information for a mobiledevice as well, including date book (or calendar) information and recentcall information.

Mobile device 100 is a battery-powered device and includes a batteryinterface 132 for receiving one or more rechargeable batteries 130.Battery interface 132 is coupled to a regulator (not shown), whichassists battery 130 in providing power V+ to mobile device 100. Althoughcurrent technology makes use of a battery, future technologies such asmicro fuel cells may provide the power to mobile device 100.

Microprocessor 102, in addition to its operating system functions,enables execution of software applications on mobile device 100. A setof applications that control basic device operations, including data andvoice communication applications, will normally be installed on mobiledevice 100 during its manufacture. Another application that may beloaded onto mobile device 100 would be a personal information manager(PIM). A PIM has functionality to organize and manage data items ofinterest to a subscriber, such as, but not limited to, e-mail, calendarevents, voice mails, appointments, and task items. A PIM application hasthe ability to send and receive data items via wireless network 200. PIMdata items may be seamlessly integrated, synchronized, and updated viawireless network 200 with the mobile device subscriber's correspondingdata items stored and/or associated with a host computer system. Thisfunctionality creates a mirrored host computer on mobile device 100 withrespect to such items. This can be particularly advantageous where thehost computer system is the mobile device subscriber's office computersystem.

Additional applications may also be loaded onto mobile device 100through network 200, auxiliary I/O subsystem 112, serial port 114,short-range communications subsystem 122, or any other suitablesubsystem 124. This flexibility in application installation increasesthe functionality of mobile device 100 and may provide enhancedon-device functions, communication-related functions, or both. Forexample, secure communication applications may enable electroniccommerce functions and other such financial transactions to be performedusing mobile device 100.

Serial port 114 enables a subscriber to set preferences through anexternal device or software application and extends the capabilities ofmobile device 100 by providing for information or software downloads tomobile device 100 other than through a wireless communication network.The alternate download path may, for example, be used to load anencryption key onto mobile device 100 through a direct and thus reliableand trusted connection to provide secure device communication.

Short-range communications subsystem 122 provides for communicationbetween mobile device 100 and different systems or devices, without theuse of network 200. For example, subsystem 122 may include an infrareddevice and associated circuits and components for short-rangecommunication. Examples of short range communication would includestandards developed by the Infrared Data Association (IrDA), Bluetooth,and the 802.11 family of standards developed by IEEE.

In use, a received signal such as a text message, an e-mail message, orweb page download will be processed by communication subsystem 104 andinput to microprocessor 102. Microprocessor 102 will then process thereceived signal for output to display 110 or alternatively to auxiliaryI/O subsystem 112. A subscriber may also compose data items, such ase-mail messages, for example, using keyboard 116 in conjunction withdisplay 110 and possibly auxiliary I/O subsystem 112. Auxiliarysubsystem 112 may include devices such as: a touch screen, mouse, trackball, infrared fingerprint detector, or a roller wheel with dynamicbutton pressing capability. Keyboard 116 is an alphanumeric keyboardand/or telephone-type keypad. A composed item may be transmitted overnetwork 200 through communication subsystem 104.

For voice communications, the overall operation of mobile device 100 issubstantially similar, except that the received signals would be outputto speaker 118, and signals for transmission would be generated bymicrophone 120. Alternative voice or audio I/O subsystems, such as avoice message recording subsystem, may also be implemented on mobiledevice 100. Although voice or audio signal output is accomplishedprimarily through speaker 118, display 110 may also be used to provideadditional information such as the identity of a calling party, durationof a voice call, or other voice call related information.

Referring now to FIG. 2, a block diagram of the communication subsystemcomponent 104 of FIG. 1 is shown. Communication subsystem 104 comprisesa receiver 150, a transmitter 152, one or more embedded or internalantenna elements 154, 156, Local Oscillators (LOs) 158, and a processingmodule such as a Digital Signal Processor (DSP) 160.

The particular design of communication subsystem 104 is dependent uponthe network 200 in which mobile device 100 is intended to operate, thusit should be understood that the design illustrated in FIG. 2 servesonly as one example. Signals received by antenna 154 through network 200are input to receiver 150, which may perform such common receiverfunctions as signal amplification, frequency down conversion, filtering,channel selection, and analog-to-digital (A/D) conversion. A/Dconversion of a received signal allows more complex communicationfunctions such as demodulation and decoding to be performed in DSP 160.In a similar manner, signals to be transmitted are processed, includingmodulation and encoding, by DSP 160. These DSP-processed signals areinput to transmitter 152 for digital-to-analog (D/A) conversion,frequency up conversion, filtering, amplification and transmission overnetwork 200 via antenna 156. DSP 160 not only processes communicationsignals, but also provides for receiver and transmitter control. Forexample, the gains applied to communication signals in receiver 150 andtransmitter 152 may be adaptively controlled through automatic gaincontrol algorithms implemented in DSP 160.

The wireless link between mobile device 100 and a network 200 maycontain one or more different channels, typically different RF channels,and associated protocols used between mobile device 100 and network 200.A RF channel is a limited resource that must be conserved, typically dueto limits in overall bandwidth and limited battery power of mobiledevice 100.

When mobile device 100 is fully operational, transmitter 152 istypically keyed or turned on only when it is sending to network 200 andis otherwise turned off to conserve resources. Similarly, receiver 150is periodically turned off to conserve power until it is needed toreceive signals or information (if at all) during designated timeperiods.

Referring now to FIG. 3, a block diagram of a node of a wireless networkis shown as 202. In practice, network 200 comprises one or more nodes202. Mobile device 100 communicates with a node 202 within wirelessnetwork 200. In the example implementation of FIG. 3, node 202 isconfigured in accordance with General Packet Radio Service (GPRS) andGlobal Systems for Mobile (GSM) technologies. Node 202 includes a basestation controller (BSC) 204 with an associated tower station 206, aPacket Control Unit (PCU) 208 added for GPRS support in GSM, a MobileSwitching Center (MSC) 210, a Home Location Register (HLR) 212, aVisitor Location Registry (VLR) 214, a Serving GPRS Support Node (SGSN)216, a Gateway GPRS Support Node (GGSN) 218, and a Dynamic HostConfiguration Protocol (DHCP) 220. This list of components is not meantto be an exhaustive list of the components of every node 202 within aGSM/GPRS network, but rather a list of components that are commonly usedin communications through network 200.

In a GSM network, MSC 210 is coupled to BSC 204 and to a landlinenetwork, such as a Public Switched Telephone Network (PSTN) 222 tosatisfy circuit switched requirements. The connection through PCU 208,SGSN 216 and GGSN 218 to the public or private network (Internet) 224(also referred to herein generally as a shared network infrastructure)represents the data path for GPRS capable mobile devices. In a GSMnetwork extended with GPRS capabilities, BSC 204 also contains a PacketControl Unit (PCU) 208 that connects to SGSN 216 to controlsegmentation, radio channel allocation and to satisfy packet switchedrequirements. To track mobile device location and availability for bothcircuit switched and packet switched management, HLR 212 is sharedbetween MSC 210 and SGSN 216. Access to VLR 214 is controlled by MSC210.

Station 206 is a fixed transceiver station. Station 206 and BSC 204together form the fixed transceiver equipment. The fixed transceiverequipment provides wireless network coverage for a particular coveragearea commonly referred to as a “cell”. The fixed transceiver equipmenttransmits communication signals to and receives communication signalsfrom mobile devices within its cell via station 206. The fixedtransceiver equipment normally performs such functions as modulation andpossibly encoding and/or encryption of signals to be transmitted to themobile device in accordance with particular, usually predetermined,communication protocols and parameters, under control of its controller.The fixed transceiver equipment similarly demodulates and possiblydecodes and decrypts, if necessary, any communication signals receivedfrom mobile device 100 within its cell. Communication protocols andparameters may vary between different nodes. For example, one node mayemploy a different modulation scheme and operate at differentfrequencies than other nodes.

For all mobile devices 100 registered with a specific network, permanentconfiguration data such as an operator profile is stored in HLR 212. HLR212 also contains location information for each registered mobile deviceand can be queried to determine the current location of a mobile device.MSC 210 is responsible for a group of location areas and stores the dataof the mobile devices currently in its area of responsibility in VLR214. Further VLR 214 also contains information on mobile devices thatare visiting other networks. The information in VLR 214 includes part ofthe permanent mobile device data transmitted from HLR 212 to VLR 214 forfaster access. By moving additional information from a remote HLR 212node to VLR 214, the amount of traffic between these nodes can bereduced so that voice and data services can be provided with fasterresponse times and at the same time requiring less use of computingresources.

SGSN 216 and GGSN 218 are elements added for GPRS support; namely packetswitched data support, within GSM. SGSN 216 and MSC 210 have similarresponsibilities within wireless network 200 by keeping track of thelocation of each mobile device 100. SGSN 216 also performs securityfunctions and access control for data traffic on network 200. GGSN 218provides internetworking connections with external packet switchednetworks and connects to one or more SGSN's 216 via an Internet Protocol(IP) backbone network operated within the network 200. During normaloperations, a given mobile device 100 must perform a “GPRS Attach” toacquire an IP address and to access data services. This requirement isnot present in circuit switched voice channels as Integrated ServicesDigital Network (ISDN) addresses are used for routing incoming andoutgoing calls. Currently, all GPRS capable networks use private,dynamically assigned IP addresses, thus requiring a DHCP server 220connected to the GGSN 218. There are many mechanisms for dynamic IPassignment, including using a combination of a Remote AuthenticationDial-In User Service (RADIUS) server and DHCP server. Once the GPRSAttach is complete, a logical connection is established from a mobiledevice 100, through PCU 208, and SGSN 216 to an Access Point Node (APN)within GGSN 218. The APN represents a logical end of an IP tunnel thatcan either access direct Internet compatible services or private networkconnections. The APN also represents a security mechanism for network200, insofar as each mobile device 100 must be assigned to one or moreAPNs and mobile devices 100 cannot exchange data without firstperforming a GPRS Attach to an APN that it has been authorized to use.The APN may be considered to be similar to an Internet domain name suchas “myconnection.wireless.com”.

Once the GPRS Attach is complete, a tunnel is created and all traffic isexchanged within standard IP packets using any protocol that can besupported in IP packets. This includes tunneling methods such as IP overIP as in the case with some IPSecurity (IPsec) connections used withVirtual Private Networks (VPN). These tunnels are also referred to asPacket Data Protocol (PDP) Contexts and there are a limited number ofthese available in the network 200. To maximize use of the PDP Contexts,network 200 will run an idle timer for each PDP Context to determine ifthere is a lack of activity. When a mobile device 100 is not using itsPDP Context, the PDP Context can be deallocated and the IP addressreturned to the IP address pool managed by DHCP server 220.

In order to better understand the various embodiments of the systems andmethods described in this specification relating to the provision ofcode signing services, an example code signing protocol and features ofan example code signing system from the perspective of a mobile devicewill first be discussed, with reference to FIGS. 4 through 6. As notedearlier, while many of the following examples are described generallywith reference to mobile devices, embodiments described herein may beapplicable to devices other than mobile devices.

Referring to FIG. 4, a diagram illustrating an example code signingprotocol in which a code signing authority provides code signingservices to a software application developer is shown generally as 300.

A software application developer 302 creates a software application 304for mobile device 100 that requires access to one or more sensitive APIson mobile device 100. It will be understood that software applicationscomprise software code that may ultimately be executed on a mobiledevice or other computing device. Consequently, the terms “code signing”and “application signing” may be used interchangeably herein.

Software application 304 may, for example, be a Java application thatoperates on a Java virtual machine (JVM) installed on mobile device 100.An API enables software applications to interface with an applicationplatform on a mobile device or other computing device. The applicationplatform may include, for example, resources such as the devicehardware, operating system and core software and data models.Accordingly, in order to make function calls to or otherwise interactwith such device resources, software application 304 will typically needto access one or more APIs on mobile device 100. The APIs effectively“bridge” software application 304 and device resources.

In this description and the appended claims, references to API accessshould be interpreted to include access of an API in such a way as toallow a software application to interact with one or more correspondingdevice resources. Therefore, providing access to any API allows asoftware application to interact with associated device resources,whereas denying access to an API prevents the software application frominteracting with the associated resources. For example, a database APImay communicate with a device file or data storage system, and access tothe database API would provide for interaction between a softwareapplication and the file or data storage system. A user interface (UI)API would communicate with controllers and/or control software for suchdevice components as a screen, a keyboard, and any other devicecomponents that provide output to an operator or accept input from anoperator of the mobile device. In a mobile device, a radio API may alsobe provided as an interface to wireless communication resources, such asa transmitter and receiver, for example. A cryptographic API may beprovided to interact with a cryptographic module, which implementscryptographic algorithms on a device. These are merely illustrativeexamples of APIs that may be provided on a mobile device and potentiallyon other computing devices. Any of such devices may include some or allof these example APIs, or different APIs instead of or in addition tothose described above.

In general, any given API may be classified as sensitive by a mobiledevice manufacturer, or possibly by an API author, a wireless networkoperator, a device owner or operator, or some other entity that, forexample, might be affected by a virus or malicious code in a softwareapplication for the device. For instance, a mobile device manufacturermay classify as sensitive those APIs that interface with cryptographicroutines, wireless communication functions, or proprietary data modelssuch as address book or calendar entries. To protect againstunauthorized access to these sensitive APIs, software applicationdeveloper 302 is required to obtain one or more digital signatures fromthe mobile device manufacturer or other entity that classified the APIsas sensitive, or from a code signing authority 306 acting on behalf ofthe manufacturer or other entity with an interest in protecting accessto sensitive device APIs, and append the signature(s) to softwareapplication 304 as described in further detail below.

A digital signature may be obtained for each sensitive API or librarythat includes a sensitive API to which software application 304 requiresaccess. In certain implementations, multiple signatures are desirable.This would allow a service provider, company or network operator torestrict some or all software applications loaded or updated onto aparticular set of mobile devices, for example. In one multiple-signaturescenario, all APIs on a device are restricted and locked until a“global” signature is verified for a software application. For example,a company may wish to prevent its employees from executing any softwareapplications onto their devices until permission is first obtained froma corporate information technology (IT) or computer services department.All such corporate mobile devices may then be configured to requireverification of at least a global signature before a softwareapplication can be executed. Access to sensitive device APIs andlibraries, if any, could then be further restricted, to be dependentupon verification of respective corresponding digital signatures.

The binary executable representation of software application 304 may beindependent of the particular type of mobile device or model of a mobiledevice. Software application 304 may, for example, be in awrite-once-run-anywhere binary format, such as is typically the casewith Java software applications. However, it may be desirable to have adigital signature for each mobile device type or model, or alternativelyfor each mobile device platform or manufacturer, for example. Therefore,software application 304 may need to be submitted to several codesigning authorities if software application 304 targets several types ormodels of mobile devices.

In the example shown in FIG. 4, when software application developer 302requires software application 304 to be signed, software application 304is sent from application developer 302 to code signing authority 306.Code signing authority 306 may represent the mobile device manufacturer,the authors of any sensitive APIs, or possibly others that haveknowledge of the operation of the sensitive APIs to which softwareapplication 304 needs access.

While not explicitly shown in FIG. 4, in certain situations, it will beunderstood that a software application may be submitted to more than onecode signing authority. Each code signing authority may, for example, beresponsible for signing software applications for particular sensitiveAPIs, or APIs on a particular model of mobile device or set of mobiledevices that supports the sensitive APIs required by the softwareapplication. A manufacturer, mobile communication network operator,service provider, or corporate client, for example, may thereby havesigning authority over the use of sensitive APIs for their particularmobile device model(s), or for mobile devices operating on a particularnetwork, subscribing to one or more particular services, or distributedto corporate employees. A signed software application may then include asoftware application and at least one appended digital signature fromeach of the signing authorities. Although these signing authoritieswould be generating a digital signature for the same softwareapplication in this example, different signing and signatureverification schemes may be associated with different signingauthorities.

From the perspective of code signing authority 306, code signingauthority 306 will receive software application 304, and may, at itsdiscretion, sign software application 304 to allow access to one or moresensitive APIs on the mobile device. Before code signing authority 306signs software application 304, code signing authority 306 may considerthe identity of application developer 302 in determining whether or notsoftware application 304 should be signed. Code signing authority 306may also review software application 304 before signing; alternatively,code signing authority 306 may choose not to perform such a review,relying on its ability to identify the identity of software applicationdeveloper 302 for recourse in the event that software application 304 isfound to be virus-infected or to contain destructive code, for example.

If code signing authority 306 determines that software application 304may access the sensitive API(s) and therefore should be signed, then adigital signature (not explicitly shown) is generated by code signingauthority 306 and appended to software application 304, to produce asigned software application 308 that is returned to software applicationdeveloper 302. On the other hand, if code signing authority 306 refusesto sign software application 304, an appropriate response (not shown)may be returned to software application developer 302.

The digital signature is typically a tag that is generated using aprivate signature key 310 maintained solely by code signing authority306. For example, according to one signature scheme, a hash of softwareapplication 304 may be generated by code signing authority 306, using ahashing algorithm such as the Secure Hash Algorithm SHA1 for example,and then encoded with private signature key 310 to create the digitalsignature. While private signature key 310 is used to encode a hash ofinformation to be signed in this example, such as may be derived fromsoftware application 304, in variant schemes, private signature key 310may be used in other ways to generate a digital signature from theinformation to be signed or a transformed version of the information.

Signed software application 308 may then be sent to mobile device 100over a wireless network 200 for example, or otherwise loaded onto mobiledevice 100. For instance, signed software application 308 may bedownloaded to a personal computer via a computer network and loaded tomobile device 100 through a serial link, or may be acquired fromsoftware application developer 302 in another manner and loaded ontomobile device 100. Once signed software application 308 is loaded onmobile device 100, at least one digital signature of signed softwareapplication 308 will then typically be verified with a public signaturekey 312 before software application 304 is granted access to a sensitiveAPI.

Although signed software application 308 is loaded onto mobile device100, it should be appreciated by persons skilled in the art that thesoftware application that may eventually be executed on mobile device100 is software application 304. As described above, signed softwareapplication 308 typically comprises software application 304 and one ormore appended digital signatures (not shown). When the appropriatedigital signatures are successfully verified (e.g. by a virtual machineat mobile device 100), software application 304 can be executed onmobile device 100 and is permitted access to any APIs for which thecorresponding signatures have been verified.

Security protocols involving software code signing schemes typicallyrely on public and private encryption keys to provide authorization toaccess sensitive APIs and to guarantee the integrity of signedapplications. In accordance with known public key cryptographictechniques, data encrypted using a private key of a private key/publickey pair can only be decrypted using the corresponding public key of thepair, and vice-versa.

In this example, a code signing authority signs a software applicationby generating a digital signature. The digital signature is a digest(e.g. a hash) of the software application, or possibly of some dataderived from the software application, which is encoded using the codesigning authority's private key. The digital signature can then beappended to the software application.

To verify the digital signature at a mobile device or other computingdevice, the digest is obtained in a similar manner (e.g. using the samestandard hash algorithm) from the software application (to which thedigital signature is appended) that is received at the device. The codesigning authority's public key, typically stored with the sensitiveAPIs, is used to decode the appended digital signature in order toobtain what should be a matching digest for the received softwareapplication. If the digests do not match, this suggests that either thesoftware application received at the device is not the same applicationthat was signed by the code signing authority, or that the softwareapplication was not signed using the correct private key or by theproper code signing authority. The digital signature algorithms aredesigned in such a way that only someone with knowledge of the codesigning authority's private key should be able to encode a digitalsignature that can be decoded correctly (e.g. by a virtual machine atthe device) using the code signing authority's public key that isassociated with one or more sensitive APIs. Therefore, by verifying adigital signature in this way, authorization and access control tosensitive APIs and the integrity of signed applications can bemaintained.

Accordingly, public signature key 312 corresponds to private signaturekey 310 maintained by code signing authority 306, and is typicallyinstalled on mobile device 100 along with one or more sensitive APIs.Alternatively, public signature key 312 may instead be obtained from apublic key repository (not shown), using mobile device 100 or possibly apersonal computer system, and installed on mobile; device 100 as needed.Mobile device 100 computes a hash of software application 304 in thesigned software application 308, using the same hashing algorithm ascode signing authority 306, and uses the digital signature and publicsignature key 312 to recover the hash originally encoded by code signingauthority 306. The resultant locally calculated hash and the hashrecovered from the digital signature are then compared, and if thehashes are the same, the signature is verified. If software application304 was signed multiple times, each digital signature may be verified ina similar manner. Software application 304 can then execute on mobiledevice 100 and access any sensitive APIs for which the correspondingsignature(s) have been verified. This example signature scheme isprovided by way of example only, and other signature schemes, includingother public key signature schemes, may also be employed in variantimplementations.

Referring to FIG. 5, a diagram illustrating components of an examplecode signing system on a mobile device is shown generally as 320.

In respect of mobile device 100, example code signing system 320comprises a virtual machine 322 (e.g. a JVM), a plurality of softwareapplications 324 a-c, a plurality of API libraries 326 a-d, and anapplication platform 328. Application platform 328 generally includesall of the resources on mobile device 100 that may be accessed by thesoftware applications 324 a-c. Application platform 328 may include, forexample, device hardware 330, the mobile device's operating system 332,and core software and data models 334. Each API library 326 a-dcomprises one or more APIs that interface with a resource available inapplication platform 328. For instance, one API library might includeall of the APIs that interface with a calendar program and calendarentry data models. Another API library might include all of the APIsthat interface with the transmission circuitry and functions of mobiledevice 100. Yet another API library might include all of the APIscapable of interfacing with lower-level services performed by the mobiledevice's operating system 332.

Some API libraries 326 a-d may expose a sensitive API (e.g. 326 a, 326c), such as an interface to a cryptographic function or module, whileother libraries may be accessed without exposing sensitive APIs (e.g.326 b, 326 d). Similarly, some software applications 324 a-324 c may besigned software applications (e.g. 324 a, 324 c) that require access toone or more sensitive APIs, while other software applications may not besigned (e.g. 324 b). Virtual machine 322 may be an object orientedrun-time environment such as Sun Microsystems' J2ME™ (Java 2 Platform,Micro Edition) for example, which manages the execution of softwareapplications 324 a-c operating on mobile device 100, and links thesoftware applications 324 a-c to the various API libraries 326 a-d.

Software application 324 a, labeled as Application Y in FIG. 5, is anexample of a signed software application (e.g. signed application 308 ofFIG. 4). In this example, signed software application 324 a includes: asoftware application (e.g. application 304 of FIG. 4) comprising, forexample, software code that can be executed on application platform 328;one or more signature identifiers 336 a; and one or more digitalsignatures 338 a associated with the signature identifiers 336 a.Software application 324 c, and other signed software applications willtypically comprise similar components. However, the components of signedsoftware applications will be described in greater detail below withreference to software application 324 a, by way of example.

Each digital signature 338 a and associated signature identifier 336 ain signed software application 324 a may correspond to an API library326 a, 326 c that exposes at least one sensitive API to which softwareapplication 324 a requires access. In certain implementations, signedsoftware application 324 a may include a digital signature 338 a foreach sensitive API within a particular API library 326 a, 326 c. Thesignature identifiers 336 a may be unique integers or some otheridentifier capable of allowing a particular digital signature 338 a tobe associated with a specific API library, API, application platform, ormodel of mobile device 100.

API library 326 a, labeled as API Library A in FIG. 5, is an example ofan API library that exposes a sensitive API. In this example, APIlibrary 326 a includes a description string 340, a public signature key312, and a signature identifier 342. API library 326 c, and other APIlibraries that expose one or more sensitive APIs will typically comprisesimilar components. However, the components of such API libraries willbe described in greater detail below with reference to API library 326a, by way of example.

Signature identifier 342 of API library 326 a may correspond to asignature identifier (e.g. 336 a) in a signed software application (e.g.324 a). These signature identifiers enables virtual machine 322 toquickly match a digital signature (e.g. 338 a) with an API library (e.g.326 a). Public signature key 312 corresponds to the private signaturekey (e.g. 310 of FIG. 4) maintained by the code signing authority, andis used to verify the authenticity of the digital signature 338 aappended to the signed application 324 a. Description string 340 may,for example, be a textual message that is displayed on mobile device 100when the signed software application 324 a is loaded or attempts toaccess a sensitive API of API library 326 a.

Operationally, when a signed software application that requires accessto a particular sensitive API (e.g. in an API library) is loaded ontomobile device 100, virtual machine 322 searches the signed softwareapplication for an appended digital signature associated with that API.In this example, this would involve matching the specific signatureidentifier associated with a digital signature with the signatureidentifier (e.g. 342) for the corresponding API library. If the signedsoftware application includes the appropriate digital signature, thenvirtual machine 322 will verify its authenticity using the publicsignature key 312 associated with that API library. Access to thesensitive API may then be granted to the software application that wassigned, upon successful verification of the digital signature. If thesigned software application does not include the appropriate digitalsignature, then access to the sensitive API may be denied.

Optionally, even when the appropriate digital signature is successfullyverified, a mobile device operator may be prompted to provideconfirmation that the sensitive API can be accessed by the softwareapplication. In that case, a message based on description string 340 maybe displayed on a display of mobile device 100, before the softwareapplication is executed and accesses the sensitive API. For instance, amessage stating “Application Y is attempting to access API Library A”may be displayed, and the mobile device operator may be given thecontrol to ultimately grant or deny access to the sensitive API.

It will be understood by persons skilled in the art that any givensigned software application may have multiple device-specific,library-specific, or API-specific signatures, or some combination ofsuch signatures appended thereto. Similarly, different signatureverification requirements may be configured for different devices. Forexample, a digital signature may be provided with a signed softwareapplication that permits access to a given sensitive API on one mobiledevice model, but not to the same sensitive API on a different mobiledevice model. This may result in the signed software application beingpermitted access to the sensitive API on one type of mobile device butnot on another. As a further example, one mobile device may requireverification of both a global signature, as well as additionalsignatures for any sensitive APIs to which a software applicationrequires access in order for the software application to be executed. Adifferent mobile device may require verification of only a globalsignature, and yet another different mobile device may requireverification of signatures only for its sensitive APIs.

It will also be understood by persons skilled in the art that in variantimplementations, certain devices capable of receiving softwareapplications to which digital signatures are appended, including devicesin which digital signature verification is not implemented or wheredigital signature verification is optional for example, may be adaptedto permit software applications to be executed without any signatureverification.

Referring to FIG. 6, a flowchart illustrating steps in an example methodof processing signed software applications performed on the mobiledevice depicted in FIG. 5 is shown generally as 350.

At step 352, a software application (e.g. application 324 a of FIG. 5)is loaded onto a mobile device (e.g. mobile device 100 of FIG. 5). Oncethe software application is loaded, the device, using a virtual machine(e.g. virtual machine 322 of FIG. 5) for example, determines whether ornot the software application requires access to any API libraries thatexpose a sensitive API at step 354. If the software application doesrequire access to the sensitive API, then the virtual machine verifiesthat the software application includes a valid digital signatureassociated with the sensitive API (or associated API library) to whichaccess is required, as described below with reference to steps 356through 366. If not, then the software application is linked with all ofits required API libraries and executed at step 368.

In this example, at step 356, the virtual machine retrieves the publicsignature key (e.g. public key 312 of FIG. 5) and the signatureidentifier (e.g. signature identifier 342 of FIG. 5) for thecorresponding API library. At step 358, the signature identifier for theAPI library is then used by the virtual machine to determine whether ornot the software application has an appended digital signature (e.g.digital signature 338 a of FIG. 5) with a corresponding signatureidentifier (e.g. signature identifier 336 a of FIG. 5). If not, then thesoftware application has not been approved for access to the sensitiveAPI by the appropriate code signing authority, and the softwareapplication may be prevented from being executed at step 360, oralternatively (not explicitly shown in FIG. 6), the software applicationmay be purged from the mobile device, or executed to the extent possiblewithout accessing the sensitive API. A user may be prompted for inputbefore any of these alternative actions (where made available) aretaken, to provide user control over the specific action to be performed(not shown).

If a digital signature corresponding to the sensitive API has beenappended to the software application and is located by the virtualmachine, then the virtual machine uses the public signature key toverify the authenticity of the digital signature at step 362. This stepmay be performed, for example, by using the signature verificationscheme described with reference to FIG. 4, or other alternativesignature schemes. If the digital signature does not successfullyverify, then the software application is either not executed, purged, orrestricted from accessing the sensitive API, as described above withreference to step 360. If the digital signature is successfullyverified, however, then optionally, a message based on a descriptionstring associated with the sensitive API or corresponding API library(e.g. description string 340 of FIG. 5) is displayed to a mobile deviceoperator at step 364, warning that the software application requiresaccess to a sensitive API, and at step 366, optionally prompting theoperator for authorization to execute the software application. Ifexecution is authorized, then the software application may be executedand linked to the sensitive API at step 368, otherwise the softwareapplication is either not executed, purged, or restricted from accessingthe sensitive API, as described above with reference to step 360.

When more than one digital signature needs to be verified for a givensoftware application, then steps 354 through 366 may be repeated foreach digital signature prior to execution of the application.

Embodiments described herein relate generally to a system and method forproviding code signing services. As noted earlier, code signing servicesmay be provided by a code signing authority (e.g. code signing authority306 of FIG. 4) to software application developers (e.g. applicationdeveloper 302 of FIG. 4) or other individuals or entities that wish tohave software applications digitally signed, so that the applicationsmay access sensitive APIs when they are executed on a computing device(e.g. mobile device 100 of FIG. 4). Examples of entities that might actas code signing authorities may include mobile device manufacturers, APIauthors, wireless network operators, device owners or operators, anyother entities that might be affected by a virus or destructive code insoftware applications for the computing device or that might otherwisewish to control access to sensitive APIs, and representatives of any ofthe above entities.

From the perspective of the code signing authority, any given softwareapplication developer (or other individual or entity that wishes to haveits applications signed) is initially an untrusted client. Until a trustrelationship is established between the software application developerand the code signing authority, the code signing authority will usuallyrefuse to sign software applications received from the softwareapplication developer that may access sensitive APIs. Only afterestablishing trust relationships with software application developersmight a code signing authority be willing to sign software applications,as the code signing authority can then track which APIs it has grantedaccess to, and to which software application developers such access hasbeen granted.

Accordingly, in one embodiment, a method of providing code signingservices will comprise at least some steps relating to registering theentities that seek access to sensitive APls as controlled by the codesigning authority. These steps are performed in order to establish trustrelationships with those entities. The method of providing code signingservices may comprise additional steps relating to receiving andprocessing code signing requests from such entities.

With respect to the registration of entities by the code signingauthority, should any destructive or otherwise problematic code beeither found in a software application or suspected because of behaviorexhibited when the software application is executed on the computingdevice, the registration privileges of the corresponding softwareapplication developer (or other registered individual or entity) withthe code signing authority may be suspended or revoked. This is madepossible since the digital signature that is appended to applications bythe code signing authority provides an audit trail through which thedeveloper of a problematic software application may be identified.

Computing devices may be informed of such registration revocations bybeing configured to periodically download revocation lists, for example.If software applications for which the corresponding digital signatureshave been revoked are running on a particular computing device, thatdevice may then halt execution of any such software application andpossibly purge the software application from its local storage. Devicesmay also be configured to re-execute digital signature verifications,either periodically or when a new revocation list is downloaded, forexample.

In certain embodiments, the code signing authorities may not providerevocations lists or the like. A code signing authority may track whichsoftware application developers (or other registered individuals orentities) may or may not have their applications signed at any giventime, and rescind signing privileges of developers at its discretion. Inone example implementation, once an application has been signed by thecode signing authority, that application will remain valid even if theassociated developer's signing privileges are later rescinded. However,subsequent requests to sign applications made by that developer afterits signing privileges have been rescinded would be denied.

Referring to FIG. 7A, a flowchart illustrating steps in a method ofproviding code signing services is shown generally as 400.

While this embodiment is described generally with reference to mobiledevices by way of example, variant embodiments may be applicable toother computing devices. Moreover, while this embodiment is describedgenerally with reference to the exchange of information between a codesigning authority and software application developers, the describedembodiment can also be applicable in respect of cases where suchinformation is exchanged between the code signing authority andindividuals or entities other than software application developers.

References to steps of method 400 as being performed by the code signingauthority are, in typical implementations, performed by a softwareapplication, which has been programmed to perform the steps of method400 unless otherwise noted. In this description and in the appendedclaims, this software application programmed to perform the steps ofmethod 400 is referred to as a code signing authority application.

The code signing authority application is one component of a system forproviding code signing services that executes on a computing devicemaintained by the code signing authority (e.g. code signing authority306 of FIG. 4). The system for providing code signing services, in oneembodiment, is shown in an example network configuration 450 of FIG. 7B.In this example, the code signing authority application 452 executes ona computing device 454, which in example network 450, is a web server.Code signing authority application 452 can interact with clients in thenetwork 450 through a web interface 456 accessible via the Internet 458,for example.

The clients with which code signing authority application 452 mayinteract can include, for example, signature tool applications 460 andAPI authoring tool applications 462 executing on remote computingdevices. A signature tool application 460 can be used to communicatedata and applications to code signing authority application 452, by asoftware application developer (e.g. software application developer 302of FIG. 4) that needs to have applications signed by the code signingauthority. An API authoring tool application 462 can be used by anauthor of sensitive APIs, who needs to obtain one or more publicsignature keys from the code signing authority to protect the APIs.

It will be understood that in some embodiments, an author of sensitiveAPIs may also act as the code signing authority.

Code signing authority application 452 will also have access to at leastone client information database 464 and at least one private signaturekey store 466. Data in client information database 464 and privatesignature key store 466 may be housed on the same storage device ordistributed across multiple storage devices, which need not necessarilyreside physically on computing device 454.

It will be understood by persons skilled in the art that the componentsshown in FIG. 7B are provided by way of example only, and that computingdevice 454 will generally comprise other components in addition to thoseshown in FIG. 7B and may comprise different components in variantimplementations.

Referring again to FIG. 7A, prior to receiving code signing registrationrequests and code signing requests from software application developers,as will be discussed in greater detail with reference to further stepsof method 400, a private key/public key pair needs to first begenerated, so that the public key can be attached to the APIs (e.g.classes) that are to be protected by classifying them as sensitive. Theprivate key can be stored locally (e.g. in private key store 466 of FIG.7B) by the code signing authority for later use. Accordingly, at step410, which is performed prior to any steps involving code signing, acode signing authority application creates a private key/public key pairfor the APIs that the code signing authority wishes to control accessto. A key pair may be generated for each individual sensitive API to beprotected, or the same key pair may be applied to multiple APIs, forexample. As further examples, different key pairs may be generated forAPIs on different devices, or for APIs on different models of the sametype of device. Step 410 is described in greater detail with respect toexample embodiments, with reference to FIGS. 8A through 8C.

Referring to FIG. 8A, in one embodiment, there is provided a means fordetermining and displaying the randomness quality of random numbersgenerated by a random data service on a computing device. It isunderstood that when a public key cryptosystem is used to generate keypairs for example, one needs a good source of random numbers for keygeneration. Generally, the more random the number, the stronger thegenerated key will be. A good source of random numbers produces numbersthat are unknown and unpredictable by potential adversaries. Inprinciple, random numbers derived from a physical process may be best,since many physical processes appear truly random.

In this embodiment, a random data service is provided that is madeaccessible to the code signing authority application for generatingpublic key/private key pairs. The random data service may gather randomdata derived from a few different sources, including serial ports,windows cryptographic APIs, keyboard and mouse events, and hardwaretokens, for example. The random data service is adapted to provide threeprimary functions: to gather random data, to provide random data toapplications that request it, and to provide a measure of the randomnessquality of the random data it has gathered.

At step 411, the randomness quality of the data provided by the randomdata service is determined. In this embodiment, random data that can beprovided upon request is continuously gathered by the random dataservice. For example, while the random data service executes, randomdata may be generated in predefined-sized blocks (e.g. 20,000-byteblocks) continuously. At this step, the generated random data isconsidered (e.g. continually, by polling the random data service at someinterval, such as once every 0.5 s), and statistical randomness testscan be applied to the sequence of random data blocks. Various randomnesstests (e.g. a Federal Information Processing Standard (FIPS) test, FIPS140-2) are known, and one or more of such tests may be applied tofacilitate a determination of the quality of the generated random data.

Depending on the randomness test used, and the manner in which resultsare provided by that randomness test, it may be possible to map eachresult onto one of a number of pre-defined, qualitative measures ofrandomness quality. For example, the random data service may apply apredefined mapping in order to indicate the randomness quality at anygiven time as satisfying one of the following states: unknown,unacceptable, poor, acceptable, good, excellent, error. At step 412,this indication of randomness quality may be displayed to a user of thecode signing authority application (e.g. an administrator of the codesigning authority).

While an indication of randomness quality may be displayed using thenames of one of the above-mentioned states, different identifiers mayalso be used. These states may also be further mapped into a fewernumber of collective states, each identified by a descriptiveidentifier, in variant embodiments.

For example, in one embodiment, the randomness quality is represented asa color in a traffic light icon, which can be displayed in a userinterface at step 412. This manner of representing randomness quality isintuitive and easy for a user to understand. Most users will be familiarwith the traffic light icon, and this image can be used to portray thecurrent quality of randomness of the numbers that will be used to createkey pairs for code signing applications.

The traffic light icon is used to illustrate the current level ofrandomness quality, and can display one of three colors (e.g. red,yellow, green) based on the current level. Red represents a state inwhich keys should not be created because the randomness quality is verypoor, or because the randomness quality cannot otherwise be verified asbeing good. Yellow represents a state in which the quality is poor, andone where it would not be recommended that keys be generated in asecurity-conscious application. Green represents a good quality ofrandomness, and users are advised that it is relatively safe to createkeys.

One possible mapping of the seven initial states noted above into acolor for the traffic light icon may be as follows:

-   -   Red: {unknown, unacceptable, error}    -   Yellow: {poor}    -   Green: {acceptable, good, excellent}        It will be understood by persons skilled in the art that other        initial state sets and further mapped state sets may be defined        in variant embodiments, and how they are predefined may depend        on the specific randomness test(s) employed.

An example dialog box of a user interface in which the traffic lighticon is displayed is shown in FIG. 8B. A descriptive identifier (e.g.based on one of the seven initial steps, or a different identifiercorresponding to the color of the light being displayed) may also bedisplayed with the traffic light icon as shown. The color of the trafficlight icon may be presented to a user in other ways. For example, thetraffic light icon displaying a color, or only a colored circle, may bedisplayed in miniature on a toolbar.

After an indication of the randomness quality is displayed at step 412,a user of the code signing authority application may direct theapplication to create a key pair for signing (e.g. by clicking the“Create Key Pair” button of the dialog box shown in FIG. 8B). In thatcase, an instruction is received from the user to create a key pair. Inone embodiment, the user may choose to create a key pair regardless ofthe state depicted by the traffic light icon. However, in variantembodiments, the option to create keys that is displayed to the user maybe disabled when a “Red light” and/or a “Yellow light” is shown.Moreover, users may be asked to confirm their selections if aninstruction to create a key pair is received while a Red and/or Yellowlight is shown, in variant embodiments.

At step 414, a private key and a corresponding public key are created inknown manner (e.g. using an RSA algorithm). At step 415, the private keyis stored for future use by the code signing authority (e.g. in privatekey store 466 of FIG. 7B), and the public key is deployed. The publickey can be attached to sensitive API(s) that the code signing authoritywishes to protect, or it may store the public key in a repository, whichis made available to code signing system components executing on,computing devices when signature verification is required. In FIG. 8C,an example dialog box is shown, where users of the code signingauthority application can send a created public key to API authors (e.g.via API authoring tool 462 of FIG. 7B) to embed in their APIs, in orderto protect those APIs.

It will be understood by persons skilled in the art that the featuresreferred to in the description of FIG. 8A, including the displayabletraffic light icon, for example, may be implemented in otherapplications adapted to use random numbers, for generating objects otherthan key pairs for code signing. For instance, these features may beemployed in applications where personal identification numbers (PINs)are generated, or in applications where session keys (e.g. used toencrypt data in accordance with a symmetric encryption algorithm) aregenerated.

Referring again to FIG. 7A, after one or more public keys have beencreated at step 410 for association with sensitive APIs, subsequentsteps of method 400 are performed when a software application developerdevelops an application that needs to access the APIs that have beenclassified as sensitive. At step 420, a registration request is receivedby the code signing authority application from a software applicationdeveloper that wishes to access a sensitive API. This registrationrequest is then processed and a determination as to whether theregistration request should accepted. Step 420 is described in greaterdetail with respect to example embodiments, with reference to FIG. 9.

In FIG. 9, there is provided a method of registering an entity for codesigning services in accordance with one embodiment. In the exampledescribed with reference to FIG. 7A and FIG. 9, that entity is asoftware application developer, although it may be some other individualor entity. Directions to software application developers on how toregister with the code signing authority may be made available tosoftware application developers using known means (e.g. through anInternet website).

At step 421, a registration request is received by the code signingauthority application from the software application developer (“APIclients”). The registration request includes information that may beused by the code signing authority to validate the identity of thesoftware application developer. This information may include typicalidentification information (e.g. contact information), and may alsoinclude credit card information that can be verified by the code signingauthority. This information may, for example, be received through any ofa number of different bands of communication. For example, data may beexchanged via Secure Socket Layer (SSL) web forms, for example.

Information received from the software application developer is verifiedat step 422. For example, a credit card company may be contacted (e.g.electronically or otherwise) to validate the credit card informationreceived.

If the verification is not successful, an error message is returned(step 428). On the other hand, if the information is successfullyverified (e.g. if the credit card information supplied is successfullyvalidated), at step 423, a unique client ID and PIN is generated by thecode signing authority application. An account record for saving theclient ID, PIN, and other information associated with the specificsoftware application developer may be created for storage in a clientinformation database (e.g. client information database 464 of FIG. 7B)maintained by the code signing authority and accessible to the codesigning authority application.

In a variant embodiment, the PIN and/or client ID may be generated bythe software application developer instead of the code signingauthority, and shared with the code signing authority for storage atstep 423.

Upon creation of the account record associated with the softwareapplication developer, the account record may also be populated withother information that may be used to manage the software applicationdeveloper's account, to keep track of account activity, and to provideindications to specified parties when account activity occurs, forexample. In one embodiment, when an account record is created for agiven software developer, the user of the code signing authorityapplication (e.g. an administrator of the code signing authority) may beprovided with a form (e.g. via a user interface 468 as shown in FIG. 7B)that allows various details or restrictions to be associated with thatsoftware application developer's account. An example form illustratingdetails that may be updated in an account record by a user of the codesigning authority application is shown in FIG. 10. Some of the detailsof the account record may be populated automatically with pre-determineddefault values.

Details that may be saved in an account record associated with asoftware application developer may include, for example, data needed tosend e-mail notifications to specified e-mail addresses (e.g. a “To:”address, a “cc:” address, a “bcc:” address, etc.). Flags may also be setto send an e-mail notification to the specified address(es) whenever aregistration attempt occurs, whenever a code signing request is made,whenever an error occurs in processing a registration attempt or a codesigning request, and/or whenever any irregular behavior (as may bedefined in the code signing authority application) is detected to haveoccurred. Flags may also be set to send an e-mail notification wheneversome other predefined event occurs. E-mail notifications allow softwareapplication developers, administrators, or other parties to monitor anaccount (e.g. their own account or another account), and in particular,to observe whether unauthorized code signing requests or registrationattempts are being made under the account.

Other details that may be saved in an account record may include thesetting for a flag that indicates that an expiry date is to beassociated with the account, and the associated expiry date. These maybe set by an administrator of the code signing authority, for example.

Other details that may be saved in an account record may include thesetting for a flag that indicates that the account is to be granted onlya specified number of allowable code signing requests, and theassociated number of allowable code signing requests. These may also beset by an administrator of the code signing authority, for example. Thismay facilitate the provision of “pay-per-use” code signing services bythe code signing authority. Accordingly, in one example implementation,a software application developer can have an application signed only solong as his account has not expired and there are allowable code signingrequests (e.g. credits) remaining.

At step 424, the client ID and PIN, and potentially other registrationdata, are transmitted to the software application developer. Whileinformation in the registration request is received at step 421 over afirst band of communication (e.g. an SSL connection), and the client IDand the other registration data (except the PIN) may be transmitted backto the software application developer over the same band ofcommunication at step 424, in one embodiment, the PIN is insteadcommunicated to the software application developer using an out-of-bandcommunication means (e.g. by telephone, by fax, etc.). This out-of-bandcommunication means is different from the band of communication used totransmit the client ID and the other registration data to the softwareapplication developer at step 424.

In the variant embodiment mentioned earlier, in which the PIN and/orclient ID is generated by the software application developer instead ofthe code signing authority, use of this externally generated PIN and/orclient ID may then be confirmed or denied at step 424. If use of theparticular PIN and/or client ID is denied, an error message may bereturned to the software application developer (flow to step 428 notshown).

At step 425, a registration file is received by the code signingauthority application from the software application developer, whichconstitutes an actual registration attempt by the software applicationdeveloper. The registration file includes the client ID and PIN that wastransmitted to the software application developer at step 424, a publickey that corresponds to a private key that only the software applicationdeveloper is expected to possess, and possibly other data. In oneembodiment, the registration file is received via an SSL connection.

For greater clarity, the public key/private key pair referred to at step425 is unrelated to the private key/public key pair that is generated tosign and verify software applications as described with reference toFIG. 4. Instead, the public key received from the software applicationdeveloper at step 425 is one part of a private key/public key pair (e.g.that may have been issued by a certification authority) used to exchangeencoded messages between the software application developer and thirdparties to facilitate secure communications. In this context, the publickey for secure communications can be subsequently used by the codesigning authority application to verify messages, such as code signingrequests, which are received from the software application developer. Infact, the registration file received at step 425 may, itself, bedigitally signed using the software application developer's private keyof secure communications.

The registration file received at step 425 contains not only the clientID transmitted to the software application developer at step 424 througha first communication band, but also the PIN that was communicated tothe software application developer through a second, “out-of-band”communication means in accordance with an example embodiment. By usingdifferent communication channels to transmit registration details to thesoftware application developer, there is a lower risk that third partiesmay come to know both the client ID and the correct PIN associated withthat client ID.

When the client ID and correct PIN associated with that client ID arereceived at step 425 and successfully verified at step 426 by the codesigning authority (i.e. the client ID and PIN in the registration filematch the client ID and associated PIN for the software applicationdeveloper as stored in the appropriate account record of the clientinformation database), then it can be more safely assumed that thepublic key for secure communications which accompanies the receivedregistration file does, in fact, correspond with a private key forsecure communications held by the software application developer. Thepublic key can be subsequently used by the code signing authority toverify messages that are purported to originate from the softwareapplication developer, and thus the use of public key cryptography toencode such messages provides enhanced security in communications. Inparticular, there would be a lower risk that a third party would be ableto complete a false registration by using an intercepted client ID andPIN, and its own public key.

In variant embodiments, different information other than the PIN may betransmitted to the software application developer over the second,preferably “out-of-band” communication means. However, in these variantembodiments, the information verified by the code signing authorityshould nevertheless comprise some details that were transmitted to thesoftware application developer through one communication means, and someother details that were transmitted to the software applicationdeveloper through some other communication means, so that at least someof the advantages noted above may be realized.

As a further security measure, in one embodiment, the code signingauthority application is adapted to keep track of the number ofregistration attempts made against any given software applicationdeveloper's account. After a predefined number of unsuccessfulregistration attempts are made against an account, that account may bedisabled. This is to prevent a brute force attack on the PIN that isshared (e.g. at step 424) between the code signing authority applicationand the software application developer.

As noted earlier, verification of the registration file is attempted bythe code signing authority at step 426 (e.g. by matching the client IDand PIN received with those in saved in the corresponding accountrecord), and a determination is made if the verification is successful.If so, then the account record associated with the software applicationdeveloper is updated to reflect a successful registration at step 427;if not, an error message may be returned to the software applicationdeveloper at step 428. Specifically, at step 427, the account record maybe updated with the public key received at step 425, for example. Thispublic key is stored in the account record of the software applicationdeveloper in the client information database, and may be used in thefuture to verify communications, including code signing requests, whichmay be received from the software application developer by the codesigning authority application.

Referring again to FIG. 7A, after a software application developer issuccessfully registered at step 420, software applications willtypically then be submitted for signing to the code signing authority bythe software application developer.

At step 430, a code signing request is received from a requestor, whichis a software application developer in this example. The code signingrequest may include, for example, the client ID associated with theaccount of the software application developer, as well as theapplication to be signed. In one embodiment, a digital signature of thesoftware application developer accompanies the code signing request,wherein the code signing request has been signed using the softwareapplication developer's private key. This facilitates authentication ofthe identity of the software application developer.

At step 440, the code signing authority application verifies that thecode signing request received at step 430 is a valid request made from aregistered software application developer. This step may comprise, forexample, obtaining the public key associated with the received client IDand verifying the digital signature appended to the code signingrequest, confirming that the account identified by the client ID has notexpired, and confirming that there are a sufficient number of creditsindicating allowable code signing requests remaining for that account.

If it is determined that a valid request is being made, then at step470, the account record associated with the account identified by theclient ID is updated. This may comprise decrementing the number ofallowable code signing requests remaining, for example. In someembodiments, information relating to the request may also be saved in alog, which may be stored in the client information database (e.g. 464 ofFIG. 7B) or on some other storage device.

At step 472, notification e-mails may be sent to addresses identified inthe account record in accordance with the settings in the accountrecord,

At step 474, the application is signed by the code signing authorityusing the private signature key created for code signing (e.g. ascreated at step 410 and stored in the private key database 466 of FIG.7B). The digital signature is also returned to the software applicationdeveloper at step 474, so that the digital signature may be appended tothe application that has been programmed to access sensitive APIs thatare protected with the corresponding public signature key. The codesigning authority application may also be configured to forward the filecontaining the digital signature to other parties at this step.

In embodiments where the code signing authority may control access todifferent APIs protected by different public signature keys, indicationof the digital signatures that need to be generated may be included in acode signing request, and the appropriate private signature key can beused accordingly to sign the application at step 474.

If it determined at step 440 that a valid request has not been made,then an error message is returned at step 480. A notification e-mail maybe sent at this step depending on the account settings.

It will be understood that any actions taken by a user of the codesigning authority application (e.g. an administrator), including themodification of account records or the initiation of a code signing keypair creation for example, may be conditional upon successfulverification of a user password or upon the provision of some otheraccess control mechanism.

It will be understood that steps 430 through 480 may be repeated wheremultiple code signing requests are received from the same softwareapplication developer, and that steps 420 through 480 may be repeatedwhere code signing services are provided to multiple softwareapplication developers.

While a digital signature generated by the code signing authority isdependent upon authentication of the software application developer andconfirmation that the software application developer has been properlyregistered in at least some of the embodiments described herein, it willbe understood that the digital signature is generated from a hash orotherwise transformed version of the software application and istherefore application-specific. This is in contrast to some known codesigning schemes in which API access is granted to all softwareapplications received from trusted software application developers orauthors, without regard to the specific application being signed. In theembodiments of the systems and methods described herein, API access isgranted on an application-by-application basis and thus can be morestrictly controlled or regulated.

In at least some example embodiments described herein, the code signingauthority receives a software application from a software applicationdeveloper for signing with a code signing request. That application isthen signed by the code signing authority once the identity of the codesigning requestor is authenticated, and certain account information ofthe requestor has been verified. Signing of the application typicallyinvolves the generation of a hash (or otherwise transformed version ofthe software application) by the code signing authority, and thesubsequent encoding of the hash with the appropriate private signaturekey.

However, in another embodiment, the application to be signed by the codesigning authority is not received as part of the code signing request.Instead, a hash (or otherwise transformed version of the softwareapplication) is received with the code signing request, where the hashhas been generated by an individual or entity other than the codesigning authority, such as the software application developer himselffor example, using the same hashing algorithm that the code signingauthority would have otherwise used had the actual application beenreceived by the code signing authority for signing. The hash can then(subject to account verification) be encoded using the appropriateprivate key by the code signing authority. Since the originalapplication is never received by the code signing authority in thisembodiment, software application developers need not fear disclosingconfidential algorithms or data. Furthermore, the code signing authoritymay benefit since any risks associated with the applications may be leftto remain with the software application developers. The code signingauthority would then typically be under no obligation to check or verifycode integrity, or to ensure that privacy policies are adhered to, forexample, since it never receives the actual applications that it wouldsign. This technique also reduces the amount of data that the codesigning authority application needs to handle when processing codesigning requests.

The steps of one or more of the methods described herein may be providedas executable software instructions stored on computer-readable media,which may include transmission-type media.

The invention has been described with regard to a number of embodiments.However, it will be understood by persons skilled in the art that othervariants and modifications may be made without departing from the scopeof the invention as defined in the claims appended hereto.

1. A method of registering entities for code signing services, themethod performed at a first computing device, the method comprising:creating at least one public key and at least one corresponding privatekey, wherein each public key and corresponding private key is associatedwith an application programming interface that has been identified assensitive; deploying each public key so that the public key is attachedto a sensitive application programming interface or sent to a requestorto embed in the sensitive application programming interface, and storingeach corresponding private key; registering at least one entity for codesigning services; receiving, from a second computing device remote fromsaid first computing device, a code signing request to sign a softwareapplication or hash thereof from the requestor, the software applicationaccessing the sensitive application programming interface when run on amobile device, said requestor being an entity registered at saidregistering, and wherein the code signing request comprises the softwareapplication or hash thereof that the requestor is requesting to havesigned with that private key, amongst the at least one private keycreated, that is associated with said sensitive application programminginterface; digitally signing the software application or hash thereof,wherein a digital signature is generated using said private keyassociated with said sensitive application programming interface; andtransmitting said digital signature to said requestor; wherein saidregistering comprises: receiving a registration request from an entityrequesting registration for code signing services, wherein saidregistration request comprises data associated with an identity of saidentity; authenticating the identity of the entity by validating at leasta subset of said data in said registration request; generating anaccount record for the entity, wherein said account record comprises atleast a first and a second identifier associated with said entity;transmitting one of the first and second identifiers to said entity viaa first communication channel and the other of the first and secondidentifiers via a different, second communication channel; receiving aregistration file from said entity; and confirming that saidregistration file comprises at least both of said first and secondidentifiers prior to accepting said registration request; and whereinsaid registering is performed prior to said receiving the code signingrequest.
 2. The method of claim 1, wherein the first identifiercomprises a client identifier and wherein the second identifiercomprises a personal identification number.
 3. The method of claim 2,further comprising generating the client identifier and the personalidentification number.
 4. The method of claim 2, wherein at least one ofthe client identifier and the personal identification number aregenerated by the entity and included in the registration request.
 5. Themethod of claim 1, wherein the data associated with the identity of theentity comprises credit card information associated with the entity, andwherein authenticating the identity of the entity comprises validatingsaid credit card information.
 6. The method of claim 1, wherein thefirst communication channel comprises a secure socket layer connection.7. The method of claim 6, wherein the second communication channelcomprises one of telephone and fax.
 8. The method of claim 1, whereinthe registration file comprises a public key associated with the entity,and wherein the method further comprises storing the public key forfuture verifications in which the public key is used to verify a digitalsignature received from the entity.
 9. A non-volatile computer-readablestorage medium comprising instructions, wherein said instructions areexecutable on a first computing device, wherein when said instructionsare executed by a processor, the processor is configured to perform aplurality of acts comprising: creating at least one public key and atleast one corresponding private key, wherein each public key andcorresponding private key is associated with an application programminginterface that has been identified as sensitive; deploying each publickey key so that the public key is attached to a sensitive applicationprogramming interface or sent to a requestor to embed in the sensitiveapplication programming interface, and storing each correspondingprivate key; registering at least one entity for code signing services;receiving, from a second computing device remote from said firstcomputing device, a code signing request to sign a software applicationor hash thereof from the requestor, the software application accessingthe sensitive application programming interface when run on a mobiledevice, said requestor being an entity registered at said registering,and wherein the code signing request comprises the software applicationor hash thereof that the requestor is requesting to have signed withthat private key, amongst the at least one private key created, that isassociated with said sensitive application programming interface;digitally signing the software application or hash thereof, wherein adigital signature is generated using said private key associated withsaid sensitive application programming interface; and transmitting saiddigital signature to said requestor; wherein said registering comprises:receiving a registration request from an entity requesting registrationfor code signing services, wherein said registration request comprisesdata associated with an identity of said entity; authenticating theidentity of the entity by validating at least a subset of said data insaid registration request; generating an account record for the entity,wherein said account record comprises at least a first and a secondidentifier associated with said entity; transmitting one of the firstand second identifiers to said entity via a first communication channeland the other of the first and second identifiers via a different,second communication channel; receiving a registration file from saidentity; and confirming that said registration file comprises at leastboth of said first and second identifiers prior to accepting saidregistration request; and wherein said registering is performed prior tosaid receiving the code signing request.
 10. A system for registeringentities for code signing services, comprising a client informationdatabase for storing a plurality of account records, wherein said systemcomprises a processor of a first computing device configured to: createat least one public key and at least one corresponding private key,wherein each public key and corresponding private key is associated withan application programming interface that has been identified assensitive; deploy each public key so that the public key is attached toa sensitive application programming interface or sent to a requestor toembed in the sensitive application programming interface, and to storestoring each corresponding private key; register at least one entity forcode signing services; receive, from a second computing device remotefrom said first computing device, a code signing request to sign asoftware application or hash thereof from the requestor, the softwareapplication accessing the sensitive application programming interfacewhen run on a mobile device, said requestor being an entity registeredat said registering, and wherein the code signing request comprises thesoftware application or hash thereof that the requestor is requesting tohave signed with that private key, amongst the at least one private keycreated, that is associated with said sensitive application programminginterface; digitally sign the software application or hash thereof,wherein a digital signature is generated using said private keyassociated with said sensitive application programming interface; andtransmit said digital signature to said requestor; wherein to registersaid at least one entity, said processor is configured to: receive aregistration request from an entity requesting registration for codesigning services, wherein said registration request comprises dataassociated with an identity of said entity; authenticate the identity ofthe entity by validating at least a subset of said data in saidregistration request; generate an account record for the entity, whereinsaid account record comprises at least a first and a second identifierassociated with said entity; transmit one of the first and secondidentifiers to said entity via a first communication channel and theother of the first and second identifiers via a different, secondcommunication channel; receive a registration file from said entity; andconfirm that said registration file comprises at least both of saidfirst and second identifiers prior to accepting said registrationrequest; and wherein said processor is configured to register said atleast one entity prior to receiving the code signing request.
 11. Thesystem of claim 10, wherein the first identifier comprises a clientidentifier and wherein the second identifier comprises a personalidentification number.
 12. The system of claim 11, wherein the processoris further configured to generate the client identifier and the personalidentification number.
 13. The system of claim 11, wherein at least oneof the client identifier and the personal identification number aregenerated by the entity and included in the registration request. 14.The system of claim 10, wherein the data associated with the identity ofthe entity comprises credit card information associated with the entity,and wherein the processor is configured to authenticate the identity ofthe entity by validating said credit card information.
 15. The system ofclaim 10, wherein the first communication channel comprises a securesocket layer connection.
 16. The system of claim 15, wherein the secondcommunication channel comprises one of telephone and fax.
 17. The systemof claim 10, wherein the registration file comprises a public keyassociated with the entity, and wherein the processor is furtherconfigured to store the public key for future verifications in which thepublic key is used to verify a digital signature received from theentity.